Double-Take Availability Release Notes

Double-Take Availability version 4.7.0, November 12, 2010

© 1996-2010 Double-Take Software, Inc. All rights reserved.

This readme file contains last minute release notes about Double-Take Availability that are not included in the user documentation. The user documentation is available on the product CD and in the installation directory after you have installed Double-Take Availability.

Be sure to check the readme file posted on the product updates download page of the Double-Take Software support web site for the latest release notes. The readme file contained in the self-extracting zip file or on the CD may not contain all of the most recent information.

Contents

Overview

This release is an updated release that includes, but may not be limited to, the following features.

  1. Operating system/distribution support—Double-Take Availability now supports Red Hat Enterprise Linux version 5.5 and 6.0, SUSE Linux Enterprise 11.1, CentOS version 5.5, and Oracle Enterprise Linux version 5.5.
  2. File system support—Double-Take Availability now supports Ext4 and XFS file systems.
  3. Restoration Wizard—Double-Take Availability now contains a Restoration Wizard to walk you through the restoration process. This wizard can be used to restore an entire server or only specific files from your replication set. In addition, the wizard can be used to restore high availability data jobs before failing back, which will decrease user downtime.

This release is an updated release that supersedes all previous releases. You can safely upgrade to this release from any previous Double-Take Availability release.

Known Issues

Installation and configuration

  1. Double-Take Availability does not directly support nested mount points. If you mount one mount point as DTFS, that mounting will not extend the DTFS layer to the nested mount points. You must mount each mount point as DTFS individually, when using a nested mount point configuration.
  2. If you uninstall the software while there is an active Double-Take Availability connection, you must reboot the server before reinstalling the software again. This issue may be resolved in a later release.
  3. DTFS will fail to mount on fifth subdirectory levels and lower. This issue may be resolved in a future release.
  4. If you are using SLES version 9.x and you want to export /data over NFSv3 and you have DTFS mounted at /data/dtfs, you may find that your NFS clients cannot see any data in /data/dtfs. To work around this issue, include both /data and /data/dtfs in your /etc/exports file.
  5. If you are using SLES version 10.x, you may get an installation database warning regarding an exclusive database lock. You can safely disregard this message.
  6. Double-Take Availability version 4.7 does not interoperate with version 4.5. If you are upgrading from version 4.5, you will have to upgrade your both your source and target to version 4.7. If you must have version interoperability, you will have to upgrade the target to version 4.6, then the source to version 4.6, and finally the target to version 4.7.
  7. Double-Take Availability does not currently support Red Hat Enterprise Linux version 6.0 eCryptfs, which is a new operating system feature that provides data and filename encryption on a per-file basis. This limitation may be resolved in a future release.
  8. If you have installed Double-Take Availability version 4.7 on a Windows client, you must uninstall it before attempting to install any earlier Double-Take Availability version. The installation of earlier releases will not properly perform a downgrade, which may cause compatibility issues and two versions to appear in Windows Add/Remove Programs.

Replication

  1. If you have hard links in your replication set, note the following caveats.
  2. Two replication operations are sent when a file is closed. This may have a negative effect on performance. This issue may be resolved in a future release.
  3. Do not attempt to mount too many DTFS mounts (50 or more). You will receive a buffer overflow error. This issue may be resolved in a future release.
  4. If your replication set contains exclude rules for specific files, the replication set generated during the restoration process will not contain those same exclude rules. Therefore, if those excluded files exist on the target, they may be restored, potentially overwriting the files on the source. This issue may be resolved in a future release.

General functionality

  1. If you specify NoMoveAddresses with the MonitorOption DTCL command, the addresses will still be moved after failover. This issue may be resolved in a later release.
  2. When you schedule start criteria for transmission, you may see the transmission status in an error state at the scheduled start. The transmission will still continue as expected. This may be resolved in a later release.
  3. When you schedule a verification process, it may run a verification report when you save the scheduled verification settings. The scheduled verification will still process as expected. This may be resolved in a later release.
  4. If you are moving or deleting orphan files, keep in mind the following caveats.
  5. If you are using Red Hat Enterprise Linux version 4.x, do not export NFS on any subdirectories below where you mounted the DTFS driver, otherwise the source server will stop responding and you will have to reboot it. If you need to export NFS, do it at the parent directory. This is not an issue on Red Hat Enterprise Linux version 5.x. This issue may be resolved in a later release.
  6. Before verifying your Double-Take Availability data, make sure that source applications are inactive and that files in the replication set are not open. Otherwise, the verification process may show differences between the source and target.
  7. The ability to stop transmission based on a specified byte limit is currently not functional. This issue may be resolved in a later release.
  8. The target log will list orphan directories and files twice if you are previewing orphan files for a full-server connection. This issue may be resolved in a later release.

Clients

  1. The interactive text client (DTCL -i) may intermittently fail if there is no DNS entry or way for a server to resolve server names.

Documentation

  1. In order to view the online documentation, you must have one of the following browsers. 

Contact Information

Double-Take, Balance, Double-Take Availability, Double-Take Backup, Double-Take Cargo, Double-Take Flex, Double-Take for Hyper-V, Double-Take for Linux, Double-Take Move, Double-Take ShadowCaster, Double-Take for Virtual Systems, GeoCluster, Livewire, netBoot/i, NSI, sanFly, TimeData, TimeSpring, winBoot/i and associated logos are registered trademarks or trademarks of Double-Take Software, Inc. and/or its affiliates and subsidiaries in the United States and/or other countries. Microsoft, Hyper-V, Windows, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a registered trademark of Linus Torvalds. Red Hat is a registered trademark of Red Hat, Inc. All other trademarks are the property of their respective companies.

© 1996-2010 Double-Take Software, Inc. All rights reserved.